Active Directory is a directory service that stores data in the form of an object. Active Directory helps administrators to manage users and resources across a network. It is a service developed by Microsoft for Windows domain networks. Click on the link to learn more about Active Directory. In this article, we’ll learn how to install the Active Directory role on a server and then Promote a Server to a Domain Controller.

Table of Contents

Open your server manager from the start menu or run the command “ServerManager” 

Now select “Manage” on the top right side then select “Add Roles and Features.“

In the “Before You Begin” section, you need to validate the three specified tasks.

Now we have to select the installation type “Role-based or feature-based installation” and then click on “Next”.

In the server selection, you have to select your server from the “server pool” and then hit “Next”.

Now here you’ll see multiple server roles. Choose the roles essential for your deployment. Currently, as we are installing and configuring Active Directory, we are adding basic features for that purpose. So I’m just selecting “Active Directory Domain Services” Leave the settings at default, then click “Add Features”:

Note: The DNS server will automatically install in the AD Primary Domain Controller (PDC) even if you do not select the service.

Here features such as “.NET, Group Policy Management, Remote Server Administration Tools, Windows Defender, and PowerShell” will be automatically chosen by default. Depending on your specific deployment needs, you can incorporate additional roles as necessary.

After completing the previous step, you will be redirected to add the “Active Directory Domain Services” feature. Click “Next” on the installer wizard window.

In the summary section, review the selected features. If everything appears correct, proceed by clicking on the “Install” button

Note: It is a good practice to reboot your machine after installing these roles. You can also select the checkbox in the “Confirmation” option.

It’ll take a few moments to install Active Directory roles and features.

We have successfully installed the necessary roles on the server now it’s time to promote the server as a domain controller.

Open your server manager from the start menu or run the command “ServerManager” 

At the top right-hand side, locate the flag icon, click on it, and then choose “Promote this server to a domain controller.”

In the deployment configuration popup screen, you will be presented with three options: joining an existing domain, adding a new domain to an existing forest, or adding a new forest.

As we are installing the first domain controller in our network, select the last option. Click “Add a new forest”.

Functional levels define the capabilities accessible within Active Directory Domain Services (AD DS) domains or forests. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest.

Note: Functional levels do not affect which operating systems you can run on workstations and member servers that are joined to the domain or forest. You should only choose older options if you have older domain controllers in your domain or forest.

As of now, we are creating a new domain so you can select any highest-level functionality.

A Short description of these terms is mentioned on the screen. We’ll explain these terms later.

Now in the DNS option, you’ll see a warning message “A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found…” This warning occurred due to the absence of a DNS Server in the environment, and authorization has not been granted to access the Coderepublics.com Zone from the external environment (Internet) on this DNS Server. You can skip this warning as it is your first forest’s domain.

It stands for Network Basic Input / Output System. NetBIOS name will remain the same as we have specified in the domain configuration step.

When configuring your domain environment, if you type Coderepublics.com for the domain name, this request will be interpreted on the DNS Server and you’ll receive a reply. If you type only CODEREPUBLICS, without the suffix, it will be interpreted on WINS (DNS translates host names into IP addresses, while WINS resolves NetBIOS names to IP addresses), if any, and you will receive a reply in this case. If there are no WINS, the Domain is found by Broadcast message.

On a Windows operating system, you can log in using the format “[email protected]” or “CODEREPUBLICS\kuldeep.” However, for non-Microsoft products, the spelling as [email protected], which we call UPN (Universal Principle Name), is not supported, and you must use the NetBios name in the form of CODEREPUBLICS\kuldeep, which we call SamAccountName.

WARNING!: You can change the Domain NetBIOS Name information as you wish, but NEVER add the Host Name of the Server on which you install the Domain Controller as this Domain NetBIOS Name!

Here you can see the setting or the change you have made. You can also click on view script (A PowerShell script to install Active Directory.).

It is one of the last steps before installing and promoting the server as DC. If everything is okay without any error then you can click on install. You can avoid security notifications and a warning for the DNS delegation. Just make sure that there is a green tick mentioning “All prerequisite checks passed successfully”.

It’ll take time to install and the server will automatically reboot once completed.

Once the system reboots. Login with Admin credentials and open “Server Manager” then select “Tools” and you’ll see the Group policy management. This is the feature that we selected in step “6. Select Features”, which means that we have successfully promoted the server to Domain Controler.

To get the information about your Domain controller these commands are shown in the PowerShell.